Snowflake

The Snowflake integration lets you build data apps with the data your Snowflake role can access. After you connect Snowflake, v0 can inspect schemas, query tables, generate dashboards or reports, preview connected apps, and deploy apps to Snowflake.

Step 1: Prepare your Snowflake account

Before your team can connect v0 or deploy apps to Snowflake, a Snowflake account admin must enable the Snowflake App Runtime and grant the Vercel integration access to the roles that will use it.

Enable App Runtime

1. In Snowsight, select your name in the lower-left corner, then Settings.
2. Under Account, select Apps.
3. If the page shows App development is not set up, click Begin Setup and complete the setup flow.

Alternatively, see Snowflake App Runtime account admin setup for full details.

Grant roles access to the Vercel integration

This step determines who on your team can use the v0 Snowflake integration. Only Snowflake users with one of the permitted roles will be able to connect. After enabling the App Runtime, the Apps page shows a Defaults tab where you can configure the destination database, schema, query warehouse, and which roles have access.

1. On the Apps page, click the Integrations tab.
2. Find the Vercel card. If it shows Not created yet, click Setup.
3. In the Setup Vercel dialog, select the roles that should have access to the integration.
4. Click Setup.

The Vercel card will update to show Roles with access and the selected roles. Use Edit Roles to change access or Disable to remove the integration.

Step 2: Add Snowflake to your v0 team

Team owners add the Snowflake account identifiers that members are allowed to connect. This makes those accounts available as options when members connect, but does not grant anyone access — that is controlled by the roles permitted in Step 1.

1. Open your v0 team settings.
2. Go to Integrations.
3. Find Snowflake.
4. Click Add Account.
5. Enter the account identifier portion of your Snowflake URL — for example, myorg-account123 from https://myorg-account123.snowflakecomputing.com. Do not include https:// or .snowflakecomputing.com. See Snowflake's Account identifiers guide if needed.
6. Optionally add a label, such as Production or Analytics.

Step 3: Connect your Snowflake user

After a team owner configures an account, team members connect their own Snowflake user via OAuth. Each member connects independently — teammates do not inherit access from another member's connection.

1. Open a chat in the v0 team.
2. Ask v0 to create something with Snowflake, such as Create an application using Snowflake that shows AI gateway usage by models.
3. When v0 shows the Snowflake card, click Connect.
4. Select the Snowflake account for the chat.
5. Complete the Snowflake OAuth flow and choose a role with access to the data you want v0 to use.

By connecting, you authorize v0 to access Snowflake through your selected role and allow v0 to send Snowflake integration usage information to Snowflake. That information is governed by your terms with Snowflake.

You can also connect manually from the chat Connect panel by choosing Snowflake.

Step 4: Build with Snowflake data

Before writing any application code, it's worth exploring your data first. Use v0's data tools to browse what your role can actually see — this gives v0 the exact database, schema, table, and column names to use when generating code.

Explore tables and run SQL

Connected Snowflake chats can use v0's data tools to:

• Browse accessible databases, schemas, and tables.
• Preview table rows with pagination.
• Run custom SQL queries.
• Use query results as context for future prompts.

Large warehouses and broad queries can be slow or expensive. Prefer targeted queries, explicit database and schema names, and LIMIT clauses while exploring data.

Generate application code

Ask v0 to inspect your Snowflake data before generating application code. This helps v0 use the exact database, schema, table, and column names available to your role.

Example prompts:

Inspect my Snowflake schemas and show me which tables look useful for a revenue dashboard.

Build an analytics dashboard from Snowflake. First inspect the table schemas and sample rows, then use the confirmed columns.

Create a report from MY_DATABASE.PUBLIC.ORDERS grouped by week. Validate the columns before writing the query.

For generated applications, Snowflake queries must run on the server. v0 handles the connected Snowflake credentials for preview and deployment, so avoid putting Snowflake tokens in client-side code.

Step 5: Deploy to Snowflake

Make sure your chat is connected to Snowflake (Step 3) before deploying. When a chat is connected, v0 shows a Snowflake publish flow.

1. Click Publish.
2. Click Deploy to Snowflake.
3. Wait for v0 to package, build, and deploy the app.
4. Use the publish menu to visit the app or copy the app URL.

After deployment, the app is hosted on Snowflake infrastructure. Deployment logs and details are available from the publish popover when Snowflake returns them.

Troubleshooting

Snowflake is not available

If you don't see the Snowflake option in your team, the integration may not be enabled for your team yet or no account identifier has been added. Contact your team owner and ask them to complete Step 1 and Step 2.

I cannot see the tables I expected

v0 only sees the data available to your connected Snowflake role. Reconnect Snowflake and choose a role with the right warehouse, database, schema, and table permissions.

A teammate cannot preview my Snowflake app

Each member connects their own Snowflake account. Ask them to connect Snowflake from the prompt shown in the preview or from the Connect panel.

Deployment keeps failing during build

If a Snowflake deployment fails repeatedly, ask v0 to inspect Snowflake app events before trying another fix. Include the deployment error logs if you have them, then prompt v0 with:

My app is having an issue with deploying to Snowflake.
Use "snow app events" to check for issues on the Snowflake deployment.
Make changes needed to deploy the application.

Deployment fails after a Snowflake role change

Reconnect Snowflake and choose a role that has access to the required v0 integration procedures and deployment permissions. Then retry the deployment from the publish popover.